Tree

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1224

reference: 737-tree-1
name: 1224
tree-preservation-order: undefined
737-tpo-1
uprn
address-text
point: POINT (-1.008879 50.886343)
geometry: MULTIPOLYGON (((-1.008808 50.886336,-1.008811 50.886350,-1.008821 50.886362,-1.008837 50.886372,-1.008856 50.886379,-1.008878 50.886381,-1.008900 50.886379,-1.008920 50.886373,-1.008936 50.886363,-1.008946 50.886351,-1.008950 50.886337,-1.008947 50.886323,-1.008937 50.886310,-1.008922 50.886300,-1.008902 50.886294,-1.008880 50.886291,-1.008858 50.886293,-1.008838 50.886300,-1.008822 50.886310,-1.008812 50.886322,-1.008808 50.886336)))
notes
felled-date
entry-date: 2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL